Fix: Avoid duplicate pip package entries in results#1561
Fix: Avoid duplicate pip package entries in results#1561mohnjiles merged 2 commits intoLykosAI:mainfrom
Conversation
|
CLA Assistant Lite bot CLA Assistant bot All Contributors have signed the CLA. |
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses a critical parsing issue in the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request effectively resolves a crash that occurs when parsing pip show output containing multiple package definitions. The switch from a LINQ ToDictionary call to a foreach loop that processes only the first package is a direct and correct fix for the issue. The addition of a comprehensive test suite in PipShowResultsTests.cs is excellent, as it covers various scenarios including the specific bug, ensuring future regression is prevented. I have one suggestion regarding improving the parser's robustness against invalid input, but overall this is a solid improvement.
| var linesDict = new Dictionary<string, string>(); | ||
| foreach (var line in lines) | ||
| { | ||
| var split = line.Split(':', 2); | ||
| if (split.Length != 2) | ||
| continue; | ||
|
|
||
| var key = split[0].Trim(); | ||
| var value = split[1].Trim(); | ||
|
|
||
| if (key == "Name" && linesDict.ContainsKey("Name")) | ||
| { | ||
| // We've hit a new package, so stop parsing | ||
| break; | ||
| } | ||
|
|
||
| linesDict.TryAdd(key, value); | ||
| } |
There was a problem hiding this comment.
This new parsing logic correctly handles duplicate package entries. However, a potential KeyNotFoundException can still occur. If the output string is empty or contains no valid key-value pairs after filtering, linesDict will be empty. This will cause a crash on line 69 when linesDict["Name"] is accessed.
A more robust implementation would validate that linesDict contains the required 'Name' and 'Version' keys before attempting to create the PipShowResult object, throwing a more specific exception like FormatException if they are missing.
|
I have read the CLA Document and I hereby sign the CLA |
ionite34
left a comment
There was a problem hiding this comment.
Looks good! Thanks for adding the test cases for the pip outputs too.
Added new test cases to smoke out the issue that at least I was running into. There's a couple hits in existing issues given the trace:
Passes after applying the changes.